-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more info about a11y tests #76045
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Did you also want to add a blurb about skipping tests if the failures cannot be fixed but creating an issue so it gets logged? and then commenting on top of the test with the issue number?
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM , more docs are always useful. This was missing indeed!
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
Co-authored-by: gchaps <[email protected]>
@bhavyarm Do you think that would be helpful? I've seen that type of thing done for any type of test. |
@myasonik I keep explaining that process to folks who are adding new tests. Sometimes more than once. So yes? :) I will link this to meta issue on tests too. Thanks! |
@bhavyarm @rashminpawar I added the info y'all requested. What do you think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very helpful info! Thanks for doing this. Had one question/suggestion.
btw, @myasonik - pinged the wrong Rashmi :-) Thanks for adding additional docs with examples |
@gchaps Could you look this over one more time? There's been a good amount added in the last few rounds and I think it's ready from a content perspective now. |
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
docs/developer/contributing/development-accessibility-tests.asciidoc
Outdated
Show resolved
Hide resolved
Co-authored-by: gchaps <[email protected]>
…rok/new-patterns-component-use-array * 'master' of github.com:elastic/kibana: (75 commits) Remove legacy ui-apps-mixin (elastic#76604) remove unused test_utils (elastic#76528) [ML] Functional tests - add UI permission tests (elastic#76368) [APM] @ts-error -> @ts-expect-error (elastic#76492) [APM] Avoid negative offset for error marker on timeline (elastic#76638) [Reporting] rename interfaces to align with task manager integration (elastic#76716) Revert back ESO migration for alerting, added try/catch logic to avoid failing Kibana on start (elastic#76220) Test reverting "Add plugin status API (elastic#75819)" (elastic#76707) [Security Solution][Detections] Removes ML Job Settings SIEM copy and fixes link to ML app for creating custom jobs (elastic#76595) [Maps] remove region/coordinate-maps visualizations from sample data (elastic#76399) [DOCS] Dashboard-first docs refresh (elastic#76194) Updated ServiceNow description in docs and actions management UI to contains correct info (elastic#76344) [DOCS] Identifies cloud settings in reporting (elastic#76691) [Security Solution] Refactor timeline details to use search strategy (elastic#75591) es-archiver: Drop invalid index settings, support --query flag (elastic#76522) [DOCS] Identifies graph settings available on cloud (elastic#76661) Add more info about a11y tests (elastic#76045) [data.search.SearchSource] Remove legacy ES client APIs. (elastic#75943) [release notes] automatically retry on Github API 5xx errors (elastic#76447) [es_ui_shared] Fix eslint exhaustive deps rule (elastic#76392) ...
Co-authored-by: gchaps <[email protected]>
Co-authored-by: gchaps <[email protected]> Co-authored-by: gchaps <[email protected]>
Summary
The accessibility tests look a little different from other functional tests so they raise a few eyebrows. Writing some more docs to better explain them.